The other job assessors do.
Apollo reads your unit’s documents side by side, so mismatches are found before validation.
Assessment documents drift out of alignment.
A template is updated without the guide. A task is reworded and the sample answer isn’t. Nobody notices until validation, or until an auditor does.
Every document, read against every other.
Apollo reads each document against every other and shows you what doesn’t match.
Tasks that don’t match the guide
A task asks for something the guide never checks, or the other way round.
Criteria with nowhere to land
Performance criteria no task actually covers, checked when you add the unit’s specification. Auditors often check this first.
Drift between versions
A template updated without the guide, or instructions that contradict the sample answer.
Every finding names the documents to check.
Each issue names the documents involved and where, so you can go straight to it. The report also lists everything it checked.
Which documents conflict
Which two documents disagree.
Where the conflict occurs
The exact section in each document.
What material was reviewed
Everything that was checked.
Information for validation. Not the validation.
Apollo gives your validators a clear list to review. When you add the unit’s specification, it checks the unit’s elements and performance criteria, but not yet performance evidence, knowledge evidence or assessment conditions. It doesn’t do the validation or certify a unit.
Run the Unit Cross-Check on one unit.
Bring the marking guide, tasks and sample answers you already have. Nothing to rebuild.